Add io-safety keyword to xcb
#2370
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Seems okay, but the branch has conflicts. Want to rebase? |
En-En-Code
force-pushed
the
xcb-io-safety-keyword
branch
from
393eb1c to
cbe2863
Compare
|
Sorry for letting this slide so far down my priority list for how simple it was. (Well, maybe it wasn't that simple since my first rebase made a mess without fixing the conflict, but nothing a force branch reset and force push can't "fix". Hey, it got there in the end.) |
djc
approved these changes
Sep 30, 2025
Better late than never! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Thanks for getting back quickly to my response. Honestly was not expecting the quick turn-around.
Since it being merged makes issues like these within RustSec's purview, I would like to add
io-safetyas a free-form keyword, hopefully to set a precedent that I/O safety violations are problems which should be reported.